Merged
Conversation
Script size changes
Totals
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release process: auto approve
opsrelease in ArgoWhen releasing the app, the
devandopsworkflows should not require manual judgement in Argo. I had configured this in a previous PR alongsideprod-canary(3c106a6) but it turns out theprod-canaryvalue is invalid as per thecd.ymljob we consume (see https://github.com/grafana/plugin-ci-workflows/blob/main/.github/workflows/cd.yml#L283). I'm removingprod-canaryto keep it to valid values and makeopsbe auto merged.